home *** CD-ROM | disk | FTP | other *** search
- <option type="enum" id="opt/51">
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <arg_longname>
- <en>Page Drying Time</en>
- </arg_longname>
- <arg_shortname>
- <en>DryingTime</en><!-- backends only know <en> shortnames! -->
- </arg_shortname>
- <arg_execution>
- <arg_group>Adjustment</arg_group>
- <arg_order>140</arg_order>
- <arg_spot>A</arg_spot>
- <arg_substitution />
- <arg_proto> -dDryingTime=%s</arg_proto>
- </arg_execution>
- <constraints>
- <constraint sense="true">
- <driver>lx5000</driver>
- <arg_defval>ev/382</arg_defval>
- </constraint>
- </constraints>
- <enum_vals>
- <enum_val id="ev/384">
- <ev_longname>
- <en>0 sec</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>0s</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>0</ev_driverval>
- </enum_val>
- <enum_val id="ev/380">
- <ev_longname>
- <en>10 sec.</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>10s</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>10</ev_driverval>
- </enum_val>
- <enum_val id="ev/381">
- <ev_longname>
- <en>20 sec.</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>20s</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>20</ev_driverval>
- </enum_val>
- <enum_val id="ev/382">
- <ev_longname>
- <en>30 sec.</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>30s</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>30</ev_driverval>
- </enum_val>
- <enum_val id="ev/383">
- <ev_longname>
- <en>40 sec.</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>40s</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>40</ev_driverval>
- </enum_val>
- <enum_val id="ev/385">
- <ev_longname>
- <en>50 sec</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>50s</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>50</ev_driverval>
- </enum_val>
- <enum_val id="ev/386">
- <ev_longname>
- <en>60 sec</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>60s</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>60</ev_driverval>
- </enum_val>
- </enum_vals>
- </option>
-